Grand Slam 3/Grand Slam 3.iso/003/fsfan.arj/FSFAN.POL

Text File | 1994-10-13 | 16KB | 479 lines

                            FsFan Net

                       Policy and Procedure

                           Version 0.02
                            (03.Oct.94)
                       Replaces Version 0.01


                        Table of Contents


Section 1 - FsFan Net Overview
     1.1 Description
     1.2 Purpose
     1.3 Fees and Cost Sharing
          1.3.1 Cost Sharing Amendments
     1.4 Exclusion of Members
     1.5 Policy Document
     1.6 General Behaviour
     1.7 Official Language

Section 2 - FsFan Net Structure
     2.1 Basic Topology
          2.1.1 Splitting Zones
          2.1.2 Splitting Regions
          2.1.3 Splitting Nets
          2.1.4 General Information on Splitting
     2.2 Zone Addressing
     2.3 Zone Allocation
     2.4 The FlightNet Domain
     2.5 Regions
     2.6 Nets
     2.7 Net Mail Hour (NMH)
     2.8 Non-Observance of Daylight Saving Time

Section 3 - FsFan Net Administration
     3.1 Administration of FsFan Net
     3.2 Zone Coordinator - ZC
     3.3 International Coordinator - IC
     3.4 Region Coordinator - RC
          3.4.1 RC Duties
     3.5 Zone Echo Coordinator - ZEC
          3.5.1 ZEC Duties

Section 4 - The Nodelist
     4.1 Distribution
     4.2 Nodelist Structure
     4.2.1 Administration Region Node Numbers
     4.3 Archive Format
     4.4 Official Editing and Distribution

Section 5 - Obtaining a Node Number
     5.1 Responsibility of AsFlightNetnment
     5.2 Availability and Eligibility
     5.3 Exclusion
          5.3.1 Limitations of Bans
     5.4 Limit of Nodes

Section 6 - Policy Changes
     6.1 Initiating Amendents

Section 13 - Copyright and Ownership of FsFan Net
     13.1 Copyright Notice

        · This policy document was designed solely for the purpose of
          providing guidelines for certain levels of administration to
          operate in a manner which coincides with the rest of the
          network on a day to day basis.   Some portions of this
          document must be strictly adhered to and clarification is made
          at that time by suggesting a penalty for breach of policy.




Section 1 - FsFan Net Overview


1.1 Description

FsFan Net is a network, open to all and any electronic bulletin boards,
public or private, anywhere in the world to anyone using a front-end
mailer system that is capable of the FTSC standard packet and handshake
format.


1.2 Purpose

FsFan Net exists simply as a group of systems freely exchanging information
related to Aviation and Flight Simulation between some or all of the systems
listed in the FsFan Net nodelist.

FsFan Net's purpose is to provide an international medium in which people
of different cultures with interests in Aviation & Flight Simulation
can share discussion with other people. FsFan Net strives to provide this
in a friendly, open atmosphere which is obtainable without considerable
difficulty by any system in the nodelist.


1.3 Fees and Cost Sharing

There are absolutely no fees to join FsFan Net or to receive the mail other
than the costs incurred in normal pick-up or delivery of mail as charged
by your local telephone company or long distance service subscription.


1.3.1 Cost Sharing Amendments

Some geographical areas may implement cost-sharing methods by way of the
democratic process as outlined in this document. These cost-sharing
amendments are outlined in Section 11.


1.4 Exclusion of Members

There shall be no exclusion of anyone from joining FsFan Net based on race,
sex, creed, religion, age, colour, or nationality.   FsFan Net does not
exclude any individual based on their membership in other networks,
unless a common inter-network body, of which FsFan Net is a member, has
recommended a ban of the sysop.


1.5 Policy Document

This policy document contains all of the rules, regulations, guidelines,
and procedures needed at all points of administration in FsFan Net for the
complete operation of the network.   Any node may be brought up on
charges of policy violation as directed in this document.


1.6 General Behaviour

FsFan Net is based on the basic ideals of fairness and friendship.   Public
flaming will not be tolerated.   If you feel the need to flame or argue
with another individual in the network, it should be done in private so
as not to disrupt the entire network.   Putting down an individual who
is not a member of FsFan Net will also not be tolerated.


1.7 Official Language

The official language of FsFan Net is and shall remain as English.
Although this document may be freely translated into other languages,
the text, contents and intent of the clauses contained herein are to be
considered correct and proper as written and interpreted in the official
language.


Section 2 - FsFan Net Structure


2.1 Basic Topology

FsFan Net consists of a series of zones based on their geographical layout.
Within these zones are regions.   There may be a maximum of 30 regions
per zone.    In each region, there may be a maximum of 30 nets.   There
may be a maximum of 32,766 nodes in a net.   At no time should the
administrating body of the network allow a net to exceed its ability to
properly execute its purpose.


2.1.1 Splitting Zones

At such a time that either a Zone Coordinator or the International
Coordinator feels that a zone encompasses too much area to run properly
or that for any reason the zone should be split into more than one area,
the IC (International Coordinator) may, at his discretion, split the
zone and allocate a new zone number to the new zone.


2.1.2 Splitting Regions

Should a region become too congested to function properly, the ZC (Zone
Coordinator) or the RC (Region Coordinator) may opt to have the region
split.   The ZC will then split the region and as the new region a
separate region number.


2.1.3 Splitting Nets

Should a net become too congested to function properly, the RC (Region
Coordinator) or the NC (Net Coordinator) may opt to have the net
split.   The RC will then split the net and as the new net a
separate net number.


2.1.4 General Information on Splitting

In the event of any geographical area splitting, the individual
responsible for assigning the new number should also appoint a new
coordinator for the area.   In addition, the new coordinator shall be
provided with information on nodelist updates and should provide their
immediate admin uplink with a nodelist update for processing.


2.2 Zone Addressing

All zones are currently based on their geographic location.


2.3 Zone Allocation

Currently, FsFan Net has allocated one zone.   Zone numbers for future
expansion will be allocated as the need arises.  Currently, the following
zone have been allocated for use in FsFan Net:

                Zone 81  (this is for the whole world)


2.4 The FsFan Net Domain

FsFan Net currently operates and recognizes only one domain nature.
Domain usage should only contain @fsfan.ftn as the domain nature.  When
written elsewhere the name shall be written FsFan Net.


2.5 Regions

Regions are allocated by the ZC/IC by geographic location.  It is entirely
up to the ZC/IC to devise a unique scheme of numbering regions. It is
strongly recommended that the area code or country code should be used
to avoid duplication of net numbers in different zones.   Should the ZC/IC
wish to use a numbering scheme not associated with area codes or country
codes, consultation with the other RCs should be made to avoid
duplication of numbering schemes.


2.6 Nets

Nets are allocated by the RC based on geographic location.   Generally,
more than one net should not cover the same geographic area that another
net covers.   This may not be feasible should the density of a
particular area be so great that a single net would simply not cover it
effectively.

2.7 Net Mail Hour (NMH)

There is no reserved mail hour within FsFan Net, FsFan Net recognises that
echomail and netmail are both valid forms of communication and does not
distinguish between them.

2.8 Non-Observance of Daylight Saving Time

FsFan Net shall not observe Daylight Saving Time.


Section 3 - FsFan Net Administration


3.1 Administration of FsFan Net

Generally, FsFan Net will be administered on each level by an assigned
individual.   These include the zone, region, and net levels.  The ZC and IC
of FsFan Net shall oversee the entire operation of FsFan Net and maintain
the direction and intent of the network.


3.2 Zone Coordinator - ZC

The ZC shall oversee all administration objectives of the network including
new policy development, consultation with all levels of administration in
policy interpretation, network structure, and dispute and appeal mediation

(i) The ZC may, from time to time, appoint members of FsFan Net to
special committees to develop policy and technical specification.


3.3 International Coordinator - IC

The IC shall oversee all administration objectives of the network including
new policy development, consultation with all levels of administration in
policy interpretation, network structure, and dispute and appeal mediation.

(i) In addition, it is the IC's duty to promote FsFan Net in good faith to
other networks, sysops and future sysops, and the general public in any
way that he sees fit.

(ii) It shall also be the duty of the IC to produce and distribute the
FsFan Net nodelist once per month as outlined in this document.

(iii) The IC may, from time to time, appoint members of FsFan Net to
special committees to develop policy and technical specification.


3.4 Zone Coordinator - RC

Each zone in FsFan Net, must have a Region Coordinator (RC). The ZC/IC may
also be considered to be the RC in cases where the RC acts without conflict
of the ZC/IC roles (ie: zone administration).


3.3.1 RC Duties

The RC shall:

(i) compile nodelist updates for submission to the IC for compilation;

(ii) distribute the following files to the RC's in their zone for
distribution:
                - FSFNODES.xxx
                - FSFPOINT.xxx
                - FSFAN.xxx

(iii) assign new nets in their zone as needed in compliance with this
policy;

(iv) maintain the smooth flow and operation of their region in FsFan Net;

(v)  work with the ZEC to assure smooth flow of echomail in their zone;

(vi) act as an inter-zone netmail hub for the members in their region.


3.5 Zone Echo Coordinator - ZEC

Each zone in FsFan Net, may elect a Zone Echo Coordinator (ZEC). In the
case of the administration zone, the IC shall appoint an International Echo
Coordinator (IEC).


3.5.1 ZEC Duties

The ZEC shall:

(i)  distribute all mandatory echos to all downlinks in their zone;

(ii) shall make available to all downlinks all echos originating in
FsFan Net as well as optionally allowing echomail gated into another zone;

(iii) make available to any system in their zone, a list of all echomail
conferences available to the systems in their zone.


3.5.1.1 Should the zone choose, the ZC may also perform the duties of
the ZEC.


Section 4 - The Nodelist/Pointlist


4.1 Distribution

The FsFan Net nodelist and poinlist update shall be distributed monthly by the
ZCs, to the RCs, to the NCs and finally to the individual nodes.

(i) the up-to-date nodelist shall also be available for freq from the IC.

(ii) the nodelist shall be hatched into the zone via a TICK echo of the ZCs
choice;

(iii) each RC shall pass their nodelist update to the IC each and every
Thursday, no later than 10:00pm in their respective time zone.   Each
RC shall be responsible for collecting these updates, processing them, and
hatching the nodelist for distribution into their zone.    No RC shall be
allowed to edit or omit an update from another zone without written
permission from that ZC (or the IC).


4.2 Nodelist Structure

The flags and general structure of the nodelist shall conform to current
FTSC standards which presently call for a St. Louis style nodelist.

4.2.1 Administration Region Node Numbers

The following node numbers shall be reserved for administration
positions within the Zone.  New zones, when added, shall follow
the same scheme of numbering, substituting their own zone number.
The ZC and/or the IC may add other numbers as they see fit.

 81:81/0   ZC  Zone Coordinator
 81:81/1   ZC  Zone Coordinator
 81:81/2   IC  International Coordinator / Nodelist
 81:81/3   ZEC Zone Echo Coordinator
 81:81/10  Pointlist

4.3 Archive Format

The nodelist, nodediff and pointlist shall be distributed weekly in a compressed
format using the most recent version of ARC or if need be PKZIP.

(i) the naming method of the compressed file shall be as follows:

             FSFNODES                 FSFNODES.xxx
             FSFDIFF                  FSFDIFF.xxx
             FSFPOINT                 FSFPOINT.xxx

         where xxx is the last digits of the day number.


4.4 Official Editing and Distribution

No person, other than the respective Node- and Pointlist Keeper shall edit
or distribute the official release copy or any other copy for release of
the FsFan Net nodelist, nodelist update file or pointlist unless express
permission has been granted by the ZC (or the IC).

Section 5 - Obtaining a Node Number


5.1 Responsibility of Assignment

FsFan Net node numbers are given out in local nets by the NC.   It is the
job of the NC to determine that an accepted node has received a copy of
this Policy document, and that the node understands and agrees to abide
by the policies laid out herein.


5.2 Availability and Eligibility

In order for a system to obtain a FsFan Net node number, their request for
the node number must be made via netmail.    Private email and echomail
shall not be sufficient proof that the system is mail capable.


5.3 Exclusion

As per section 1.4, no individual shall be excluded from joining FsFan Net
for any reason whatsoever except in the event of an international ban
based on proven behaviour in other networks.


5.3.1 Limitations of Bans

Should an individual be banned from FsFan Net or any other network, they
shall only be banned from FsFan Net for a period not exceeding 2 years. At
this time, they may reapply for a node number in FsFan Net.


5.4 Limit of Nodes

No system shall retain a node number in more than one net within
FsFan Net.


Section 6 - Policy Changes


6.1 Initiating Amendents

Policy may be added to or changed by means of a special resolution to the IC
or your ZC.   Discussion and formulation of policy changes will be made by a
Policy Council consisting of the IC and ZCs.   Once formulated, the policy
shall be put forth to the FsFan Net membership at large for ratification.
A simple netmail message or echomail message in FSFAN.HUB to the IC and
your ZC will initiate policy discussion.

(i) should the Policy Council decide that it is in the best interest of the
membership to institute the policy prior to ratification, they may do so
with the unanimous agreement of the IC and ZCs.

(ii) the IC or any ZC may veto any policy change from going to ratification
until further discussion takes place within the Policy Council.

(iii) no single person can make ammendments, additions or deletions of
statements in this policy without first following the procedures
outlined in this Policy.

(iv) AMMENDMENT: During the introduction of this policy, Each State
Hub/Host may be asked to examine/comment on proposed changes to the
policy. Once the policy is in place, and once more than two zones
exist, Statement 6.1.iii will be deleted!


Section 13 - Copyright and Ownership of FsFan Net


13.1 Copyright Notice

FsFan Net, FSFNODES, FSFPOINTS, FsFan Net nodes and the FsFan Net Policy
Document are all trademarks and are Copyright (C) 1993 by FsFan Net. All rights
are reserved worldwide and no use of the copywritten trademarks may be used
with the prior written consent of the owner.   This copyright in no way
controls the contents of the nodelist but only the names FsFan Net
FSFNODES and FSFPOINTS.